Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1169

reference
774-tree-1
name
1169
tree-preservation-order

undefined

774-tpo-1
uprn
address-text
point
POINT (-1.044377 50.869260)
geometry
MULTIPOLYGON (((-1.044320 50.869254,-1.044323 50.869266,-1.044331 50.869276,-1.044343 50.869284,-1.044359 50.869289,-1.044377 50.869291,-1.044394 50.869289,-1.044410 50.869284,-1.044423 50.869276,-1.044431 50.869266,-1.044434 50.869255,-1.044432 50.869244,-1.044424 50.869234,-1.044411 50.869226,-1.044396 50.869221,-1.044378 50.869219,-1.044360 50.869221,-1.044344 50.869226,-1.044332 50.869233,-1.044323 50.869243,-1.044320 50.869254)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL